table of contents
CYRUS.CONF(5) | Cyrus IMAP | CYRUS.CONF(5) |
NAME¶
cyrus.conf - Cyrus IMAP documentation
Cyrus configuration file
DESCRIPTION¶
cyrus.conf is the configuration file for the Cyrus cyrus-master(8) process. It defines the startup procedures, services, events and daemons to be spawned, managed and tended to by master.
The /etc/cyrus.conf file consists of a series of entries divided into sections of the form
section {
name arguments
...
...
... }
where section is the name of the section, name is the name of the entry and arguments is the whitespace-separated list of arguments for the entry. The name may be any sequence of alphabetic and numeric characters, but may not contain punctuation such as '-' or '_'. In the SERVICES section, names must be unique.
Blank lines and lines beginning with ``#'' are ignored.
SECTION DESCRIPTIONS¶
The paragraphs below detail the four sections (START, SERVICES, EVENTS, DAEMON) that can be placed in the /etc/cyrus.conf file. The arguments that are available for each entry within the section are described, and each argument's default value is shown.
An important distinction exists between SERVICES and DAEMON ; the former have sockets which cyrus-master(8) will listen on (either IP or Unix domain) while the latter do not. Similarly, processes listed in START will be run to completion before any SERVICES are started, while those in DAEMON will be managed by cyrus-master(8).
NOTE:
Arguments can appear in any order. Some arguments have no default value, these are listed with ``<no default>''. For string arguments, the value MUST be enclosed in double quotes.
START¶
This section lists the processes to run before any SERVICES are spawned. This section is typically used to initialize databases. Master itself will not startup until all tasks in START have completed, so put no blocking commands here.
cmd=<no default>
NOTE:
SERVICES¶
This section is the heart of the /etc/cyrus.conf file. It lists the processes that should be spawned to handle client connections made on certain Internet/UNIX sockets.
babysit=0
cmd=<no default>
listen=<no default>
path [ host : ] port
where path is the explicit path to a UNIX socket, host is either the hostname or bracket-enclosed IP address of a network interface, and port is either a port number or service name (as listed in /etc/services).
If host is missing, 0.0.0.0 (all interfaces) is assumed. Use localhost or 127.0.0.1 to restict access, i.e. when a proxy on the same host is front-ending Cyrus.
Note that on most systems UNIX socket paths are limited to around 100 characters. See your system documentation for specifics.
proto=tcp
tcp4, udp4: These arguments are used to bind the service to IPv4 only.
tcp6, udp6: These arguments are used to bind the service to IPv6 only, if the operating system supports this.
tcp, udp: These arguments are used to bind to both IPv4 and IPv6 if possible.
prefork=0
maxchild=-1
maxfds=256
maxforkrate=0
EVENTS¶
This section lists processes that should be run at specific intervals, similar to cron jobs. This section is typically used to perform scheduled cleanup/maintenance.
cmd=<no default>
period=0
at=<hhmm>
DAEMON¶
This section lists long running daemons to start before any SERVICES are spawned. They will be shutdown when cyrus-master(8) is exiting.
cmd=<no default>
EXAMPLES¶
# example cyrus.conf START {
recover cmd="ctl_cyrusdb -r" } SERVICES {
imap cmd="imapd" listen="imap" prefork=1
imaps cmd="imapd -s" listen="imaps" prefork=0
lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp"
lmtp cmd="lmtpd" listen="localhost:lmtp" } EVENTS {
checkpoint cmd="ctl_cyrusdb -c" period=30
delprune cmd="cyr_expire -E 3" at=0400
tlsprune cmd="tls_prune" at=0400 } DAEMON {
idled cmd="idled" }
ACCESS CONTROL¶
When TCP Wrappers is used to control access to Cyrus services, the name of the service entry should be used as the process name in the hosts_access(5) table. For instance, in the example above, "imap", "imaps", "lmtpunix" and "lmtp" would be used as the process names. This allows a single daemon such as imapd to be run in different modes or configurations (i.e., SSL and non-SSL enabled) yet still have separate access control rules.
SEE ALSO¶
cyrus-master(8), imapd(8), pop3d(8), lmtpd(8), timsieved(8), idled(8), notifyd(8), ctl_cyrusdb(8), ctl_deliver(8), tls_prune(8), hosts_access(5)
AUTHOR¶
The Cyrus Team, Nic Bernstein (Onlight)
COPYRIGHT¶
1993-2017, The Cyrus Team
May 18, 2018 | 3.0.7 |